Adobe Acrobat End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Adobe Acrobat versions. Dates read at the vendor's own lifecycle pages (helpx.adobe.com). Updated at every deploy.
Adobe Acrobat Acrobat 2024 (Classic track) is supported until July 15, 2029, its end-of-support date. It is also the next Adobe Acrobat version to reach end of life. 8 of 10 tracked Adobe Acrobat versions are past end of life; the most recent to reach it, Acrobat 2020 (Classic track), did so on November 30, 2025. The full Adobe Acrobat lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| Acrobat 7 / Reader 7 | 7 | Dec 28, 2004 | Dec 28, 2009 | 6131 days past EOL | EOL |
| Acrobat 8 / Reader 8 | 8 | Nov 3, 2006 | Nov 3, 2011 | 5456 days past EOL | EOL |
| Acrobat 9 / Reader 9 | 9 | Jun 23, 2008 | Jun 26, 2013 | 4855 days past EOL | EOL |
| Acrobat X / Reader X | 10 | Nov 15, 2010 | Nov 15, 2015 | 3983 days past EOL | EOL |
| Acrobat XI / Reader XI | 11 | Oct 15, 2012 | Oct 15, 2017 | 3283 days past EOL | EOL |
| Acrobat 2015 (Classic track, Acrobat DC) | 2015 | Apr 7, 2015 | Jul 7, 2020 | 2287 days past EOL | EOL |
| Acrobat 2017 (Classic track) | 2017 | Jun 6, 2017 | Jun 6, 2022 | 1588 days past EOL | EOL |
| Acrobat 2020 (Classic track) | 2020 | Jun 1, 2020 | Nov 30, 2025 | 315 days past EOL | EOL |
| Acrobat 2024 (Classic track) | 2024 | Jul 15, 2024 | Jul 15, 2029 | 1008 days remaining | Active |
| Continuous track (Acrobat and Acrobat Reader) | — | — | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/adobe-acrobat)
Adobe Acrobat lifecycle status — the real story
Adobe Acrobat (Pro, Standard) and the free Acrobat Reader ship on two product tracks. The Continuous track is the subscription build that updates itself and has no end date; Adobe's support guidelines say "Adobe provides security updates to our current apps only." The Classic tracks are the perpetual or term-licensed releases that Adobe dates on its Products and technical support periods matrix: Acrobat 2024 (sold as Acrobat Classic) reached general availability on July 15, 2024 and its core support ends on July 15, 2029; Acrobat 2020 (Pro, Standard and Reader 2020) ended core support on June 1, 2025, extended by Adobe to November 30, 2025; Acrobat 2017 ended on June 6, 2022; Acrobat 2015 (the first Acrobat DC Classic release) ended on April 7, 2020, extended to July 7, 2020. The older numbered releases, Acrobat and Reader XI (ended October 15, 2017), X (November 15, 2015), 9 (June 26, 2013), 8 (November 3, 2011) and 7 (December 28, 2009), are on the same page.
Acrobat and Reader carry 24 entries in CISA's Known Exploited Vulnerabilities catalog (2026.10.08): 13 filed as 'Acrobat and Reader', 8 as 'Reader and Acrobat', 1 as 'Acrobat' (CVE-2020-9715, added April 13, 2026), 1 as 'Acrobat and Reader, Flash Player' (CVE-2009-1862) and 1 as 'Reader' (CVE-2013-0641, joined by a force override because the catalog string lacks the word Acrobat). Two are flagged as used in ransomware campaigns: CVE-2008-2992 and CVE-2010-0188 (both added March 3, 2022). The most recent additions are CVE-2026-34621 (added April 13, 2026) and CVE-2009-3459 (added May 20, 2026). Most of the catalog entries name Acrobat and Reader 7 through XI, all of which are years past Adobe's end of support.
Field mapping: support and eol are both Adobe's 'End of core support' day for the track, exactly as printed; where the cell reads 'extended until', the served day is the extended one and the originally scheduled day is kept in the cycle's vendor field. extendedSupport is false for every Acrobat track because the 'End of extended support' column prints N/A. releaseDate is the 'General availability' column. The Continuous track has no row on the matrix and is served undated. Reader 2017, Standard 2024 and Reader 2024 have no row and are not served. The matrix is on helpx.adobe.com, which blocks non-browser clients, so the page is verified by hand.
Adobe Acrobat release and support pattern
Across the 9 release lines with a published release date, Adobe Acrobat has shipped a new line roughly every 2.3 years (median interval). A line typically stays supported for about 5 years from its release to its end-of-life date (measured on the 9 lines with both dates published).
Of the 10 release lines tracked, 8 are past end of life and 2 are still within support. The next scheduled end of life is 2024 on July 15, 2029 — 1008 days from this build.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Adobe Acrobat security intelligence
CISA KEV history: Adobe Acrobat is named in CISA's Known Exploited Vulnerabilities catalog 24 times, most recently on 2026-05-20, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does Adobe Acrobat end of life mean for your organization?
When a version of Adobe Acrobat reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Adobe Acrobat should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Adobe Acrobat reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Adobe Acrobat versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Adobe Acrobat has 8 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Adobe Acrobat is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."